Presentation slide preparation

ABSTRACT

Presenting a slide. Anticipating a slide to be selected for display. Receiving data of the anticipated slide in an unconstructed format. Constructing the anticipated slide from the received data. Caching the constructed slide. Pre-drawing the constructed slide in construction memory. Receiving instructions to display a slide. In the event that the instructed slide is the cached and pre-drawn slide, rendering the pre-drawn slide to display memory.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. Provisional Pat. App. Ser.No. 61/319,694, filed on Mar. 31, 2010, the contents of which areincorporated herein in their entirety for all purposes.

FIELD

The technology disclosed herein (the “technology”) relates toprocessor-implemented presentation systems. More specifically, thetechnology relates to caching a constructed slide of a presentation.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example, to the accompanyingdrawings that show example implementations of the technology of thepresent application.

FIG. 1 is a schematic diagram of a wireless communication system;

FIG. 2 is a block diagram of components of a portable electronic device112 forming part of the communication system of FIG. 1, according to animplementation;

FIG. 3 is a block diagram showing functional components of thetechnology;

FIG. 4 is a flowchart illustrating methods of the technology, using thefunctional components of FIG. 3;

FIG. 5 is a flowchart illustrating methods of the technology, using thefunctional components of FIGS. 1-3; and

FIG. 6 is a flowchart illustrating methods of caching a ready-to-displayrepresentation of an anticipated slide in slide construction memory of apresentation device 113.

FIG. 7 illustrates a data processing system suitable for storing acomputer program product of the present technology and for executing theprogram code of the computer program product.

DETAILED DESCRIPTION

Reference will now be made in detail to implementations of thetechnology. Each example is provided by way of explanation of thetechnology only, not as a limitation of the technology. It will beapparent to those skilled in the art that various modifications andvariations can be made in the present technology without departing fromthe scope or spirit of the technology. For instance, features describedas part of one implementation can be used on another implementation toyield a still further implementation. Thus, it is intended that thepresent technology cover such modifications and variations that comewithin the scope of the technology.

Electronic slide presentations are a common way to present informationto one or more viewers. Slide presentation software (e.g. Microsoft®Office PowerPoint®) facilitates the creation of multimedia filesincorporating text, images, audio and/or visual clips for presentationin one or more slides. Often the files are presented in a slideshow,displaying the slides sequentially. The slides may be displayed to adisplay screen of a computing device (e.g., a personal computer), or viaa presentation device such as a projector for projecting thepresentation to a remote screen.

More particularly, portable electronic devices such as wireless mobiledevices (cellular phones, PDAs, etc.) among others, may include a viewerfor displaying slide presentations in multiple display modes, such as atext mode for displaying text information distilled from the slides, apreview mode for displaying thumbnail slide images rendered from theslides and a mixed mode for displaying both text information andthumbnail slide images together. The slide presentation viewer may alsoinclude a slide show mode to display the slide images in full screenalong with an interface (e.g. menu) for selecting among the multiplemodes and for invoking and controlling the slide show. For handheldwireless communication devices in particular, a network server mayprocess slide presentation files to generate the text information andslide images for communicating to wireless devices equipped withappropriate slide presentation viewers. The network server may be anattachment server providing services for email attachments and the slidepresentation viewers may be attachment viewers for email or dedicatedviewers for presentations.

Handheld communication devices may also be capable of remotelycontrolling display of an electronic slide presentation. For example, apresentation mode of operation may be provided for wirelesslycontrolling display of a slide presentation on, or through, apresentation device. When controlling a presentation in this fashion,the slides being displayed on the handheld electronic device can be thesame as those displayed on the presentation device (or on a displayconnected to the presentation device).

The term “slide” as used throughout the specification and drawingsincludes, but is not limited to, a single presentation slide (such as aPowerPoint® slide), a page in a PDF file, or a single photo image.

FIG. 1 shows a communication network system 100 comprising at least oneportable electronic device 112, an IP network 114 (including a wirelesscarrier network and base station (not shown)), a wireless networkgateway 116, an enterprise email server 117, an enterprise wirelesscommunication device server or proxy server 118, an attachment server119, a display 190, and interconnections therebetween.

The portable electronic device 112 can be operable to effectcommunications over an IP network 114 via a radio communications channel160, and can communicate with the base station (not shown) while locatedwithin a coverage area that is defined by the base station. The basestation can be part of the IP network 114, or other network such as aWireless Wide Area Network (WWAN). Data can be delivered to the portableelectronic device 112 via wireless transmission from the base station.Similarly, data can be sent from the portable electronic device 112 viawireless transmission to the base station.

It will be appreciated that the portable electronic device 112 can bemovable within the coverage area and can be moved to coverage areasdefined by other base stations. Generally, portable electronic devices112 can be connected to a wireless network that may comprise one or moreof a WWAN and a Wireless Local Area Network (WLAN) or other suitablenetwork arrangements such as 114. In some implementations, the devices112 can be configured to communicate over both the WWAN and WLAN, and toroam between these networks. In some implementations, the wirelessnetwork may comprise multiple WWANs and WLANs.

The WWAN may be implemented as any suitable wireless access networktechnology. By way of example, but not limitation, the WWAN may beimplemented as a wireless network that includes a number of transceiverbase stations where each of the base stations provides wireless RadioFrequency (RF) coverage to a corresponding area or cell. The WWAN istypically operated by a mobile network service provider that providessubscription packages to users of the mobile communication devices. Insome implementations, the WWAN conforms to one or more of the followingwireless network types: Mobitex Radio Network, DataTAC, GSM (GlobalSystem for Mobile Communication), GPRS (General Packet Radio System),TDMA (Time Division Multiple Access), CDMA (Code Division MultipleAccess), CDPD (Cellular Digital Packet Data), iDEN (integrated DigitalEnhanced Network), EvDO (Evolution-Data Optimized) CDMA2000, EDGE(Enhanced Data rates for GSM Evolution), UMTS (Universal MobileTelecommunication Systems), HSPDA (High-Speed Downlink Packet Access),IEEE 802.16e (also referred to as Worldwide Interoperability forMicrowave Access or “WiMAX”), or various other networks. Although WWANis described as a “Wide-Area” network, that term is intended herein alsoto incorporate wireless Metropolitan Area Networks (WMAN) and othersimilar technologies for providing coordinated service wirelessly overan area larger than that covered by typical WLANs.

The WWAN may further comprise, or interface with, a wireless networkgateway 116 that connects the devices 112 to transport facilities, andthrough the transport facilities to an enterprise system 120. Transportfacilities may include one or more private networks or lines, theInternet, a virtual private network, or any other suitable network. Theenterprise system 120 may be operated, for example, by an organizationor enterprise such as a corporation, university, or governmentaldepartment that allows access to a network 124 such as an internal orenterprise network (e.g., an intranet) and its resources, or theenterprise system 120 may be operated by a mobile network provider. Insome implementations, the network 124 may be realized using the Internetrather than or in addition to an internal or enterprise network.

The portable electronic device 112 can be further operable to delivercontent to and control a presentation device 113. For example, device112 can send slide presentation content and control signals to thepresentation device 113 for controlling display of a presentation, suchas a Microsoft® Office PowerPoint® presentation or successive pages ofan image attachment, such as a Portable Document Format (PDF) document.The electronic device 112 can communicate with the presentation device113 over communications link 170, e.g., a wired or wireless link.Communications link 170 between the electronic device 112 and thepresentation device 113 can be, for example, a Bluetooth® wirelesstechnology communications link.

Proxy server 118 can handle client requests from the portable electronicdevice 112 for documents stored within attachment server 119. Theattachment server 119 can communicate with the proxy server 118 totransmit attachments such as documents, spreadsheets, images, multimediafiles, etc. through the gateway 116 and network 114 for viewing via anattachment viewer of the portable electronic device 112 so as to allow auser to view attachments that are received in email messages. While onlyone attachment server 119 is shown for illustration purposes, a personskilled in the art will understand that the attachment server 119alternatively can be a network of attachment servers. Sources for theattachments stored within server 119 can include mail server 117, andmay include a web server, IM server, etc. Preferably the attachment datais downloaded to portable electronic device 112 in chunks of binary datain an attachment viewer readable format, for example Universal ContentStream (UCS) format.

Referring now to FIG. 2, a block diagram of some typical componentswithin the portable electronic device 112 is shown. In the illustratedimplementation, the portable electronic device 112 is based on thecomputing environment and functionality of a wireless personal digitalassistant (PDA). It will be understood, however, that the portableelectronic device 112 is not limited to wireless personal digitalassistants. Other portable electronic devices are possible, such assmart telephones, laptop computers, and tablet computers.

The portable electronic device 112 can include a processor 200 connectedto a read-only-memory (ROM) 210 that can contain a plurality ofapplications executable by the processor 200 that can enable theportable electronic device 112 to perform certain functions including,for example, PIN message functions, SMS message functions and cellulartelephone functions, and at least one attachment viewer application forviewing attachments (e.g. document attachments to emails or documentsfrom other sources, such as web servers, etc.). The processor 200 isalso connected to a random access memory unit (RAM) 220 and a persistentstorage device 230, which are responsible for various storage functionsof the portable electronic device 112. The processor 200 receives inputfrom input devices such as a keypad 240 and a trackball or touchsensitive input 250. The processor 200 outputs to various outputdevices, such as an LCD display 260. A microphone 270 and phone speaker280 are connected to the processor 200 for cellular telephone functions.The processor 200 is also connected to a modem and radio device 290. Themodem and radio device 290 is used to connect to wireless networks fortransmitting and receiving voice and data communications through anantenna 294. A Bluetooth® wireless technology receiver/transmitter 296is provided to effect wireless communication between device 112 andother Bluetooth-enabled devices, such as presentation device 113, asdiscussed in greater detail below. A content store 298, which isgenerally a file storage system for the portable electronic device 112,is also provided. Though not illustrated, the device 112 can includeother near-range communications interfaces, e.g., an infrared interfaceoperating similar to television remote control interface.

Request/view functionality for an attachment can be provided by theclient/server combination of attachment viewer within the portableelectronic device 112 and the attachment server 118. More particularly,with reference to FIG. 3, portable electronic device 112 can beconfigured (e.g. via software stored, for example, in ROM 210) tocomprise various components including an operating system 300, acommunications system 305 for wireless communication, an emailapplication 310 and other applications 315. Email application cancomprise or otherwise cooperate with various attachment viewers 320 forretrieving and viewing attachments. One such attachment viewer is slidepresentation viewer 325. Other viewers 330 include spreadsheet viewers,image viewers, word processing document viewers, etc. (not describedherein). Other applications 315 include other communication and controlapplications 317 and a presentation application 319 for communicatingwith and controlling presentation device 113. The presentationapplication 319 can communicate with one or more presentation devicesvia wired or wireless connections, including cables, radio frequency,and infrared media.

Attachment server 119 can be configured (e.g. via software stored, forexample, in non-volatile memory (not shown)) to comprise variouscomponents including a operating system 335, communications system 340,slide presentation attachment handler 345 as well as other attachmenthandlers 347 for other attachment types. Slide presentation attachmenthandler 345 can comprise or otherwise cooperates with a text distiller350 and slide renderer 355. Text distiller 350 can be configured toparse or otherwise review slide presentation documents to extract textinformation for delivery to handheld devices such as portable electronicdevice 112. Slide renderer 355 can define rasterized slide images (e.g.in a jpeg, tiff or other image format) from the slide presentationdocument for each slide for similar delivery.

The attachment server 119 and/or proxy server 118 and portableelectronic device 112 can communicate such that when a user invokes theattachment viewer 325 to view the content of a slide presentation, theportable electronic device 112 can transmit one or more requests forslide information, (i.e. the text information and slide images) andreceives same in response. Requests and responses are illustratednotionally as communicating directly between the portable electronicdevice 112 and attachment server 119 but it is understood thatcommunications are through network 114 via gateway 116 and proxy server118.

Due in part at least to communication protocol constraints on amessage's size, a single message may be insufficient to communicate allof the text information and/or all of the slide images for a slidepresentation document. Thus, the portable electronic device 112 can makemultiple requests either automatically or in response to direct orindirect user actions. For example, as described above, during a slideshow, the slide presentation viewer 325 can automatically make requestsfor slide information in the background while a slide show is beingviewed. For example, the viewer 325 can anticipate the need for moreslide information in response to input via trackball or touch input 250scrolling toward the end of the slides present on the handheld device.In some implementations, a menu choice may be invoked (e.g. a “More”command) for additional slide information, as applicable, to pre-loadslides.

In some implementations, a request (e.g. for slide information) includesa flag or other data indicating a screen size for the portableelectronic device 112 when rendering slide images. This can be aspecific pixel size (e.g. 340×280), a code flag (1=340×280 pixels) or adevice type, among other types, where the attachment server 119 or proxyserver 118 determines the screen size from the code flag or device type.Other display capabilities can be indicated to the attachment server 119as well or alternatively. For example, the color capabilities of thedisplay screen (e.g. back and white only or the number of colorsavailable), reflective type, etc. can be indicated to help render slideimages. The attachment server 119 then can adjust the color palette ofthe rendered slide presentation for viewing on the requesting device.

Slide presentation viewer 325 can provide a graphical user interface(GUI) to present the slides in the various modes and provides a menu orother command interface for user input to invoke the presentationapplication 319 for transmitting the slide presentation to presentationdevice 113 and controlling the presentation thereat.

More particularly, presentation device 113 can include a presentationadapter 360 for communicating with presentation application 319.

In addition to presentation adapter 360, presentation device 113includes other hardware and software such as communications 365, otherprojector applications 370 (e.g., for communicating with display 190)and operating system 375.

With reference to FIG. 4, example methods are set forth for downloadingand viewing a presentation on the portable electronic device 112, e.g.,using the functional components of FIG. 3. First, at 400, the portableelectronic device 112 can request an attachment (e.g. slidepresentation) from attachment server 119. The request can be initiated,for example, by a trackball click or menu item selection to “Openattachment” or “Download attachment.” The presentation attachment may bean attachment to an email, calendar event, instant message (IM), browserlink, or other attachment-enabled object.

If the presentation attachment has been saved to memory of the device119, e.g. a persistent store 230 or Secure Digital (SD) card (notshown), then the attachment can be retrieved locally to the device 119,and process flows continues at FIG. 5.

If the presentation attachment has not been previously requested (e.g.,a “No” at 410), attachment server 119 can build a DOM that representsthe attachment, e.g., by parsing the attachment document (step 420). Inthis manner, a graph structure can be built within attachment server 119representing a model of the original attachment file. The DOM containstextual content, font, style and formatting attributes as well as layoutattributes, such as page/slide size, positioning information (i.e. x, yand z coordinates on the page), embedded graphics and tables, forexample. DOM structure is known and is disclosed in United States PatentApplication No. 2006/0055693. Approaches other than use of DOMs torepresent a presentation are within the scope of the present technology.The DOM representation is used as an example.

Once the DOM of the attachment has been built the attachment server 119can transcerpt and encapsulate the DOM in UCS data, as indicated at 430.The UCS data then can be sent to portable electronic device 112 inchunks, as indicated at 440. Each chunk is a self-contained datarepresentation of a portion of the presentation attachment (e.g. oneimage of a slide, one slide of a presentation). That is, there issufficient data contained in a chunk to enable the attachment viewer todisplay the content of the chunk. Depending on the size of the chunksand the size of the attachment, the entire attachment can be transmittedin one chunk or in multiple chunks. Depending on the nature of therequest from the attachment viewer, attachment server 119 can transmitthe chunks in sequence or out of sequence. For example, if theattachment viewer requests the fifth slide of a presentation attachment,attachment server 119 can transmit the chunks corresponding to the fifthslide, even if chunks for slides 1 to 4 have not been transmitted to thedevice 112.

The attachment then can be previewed via display 260, and several menuor command options are made available (450) such as “Present”, “RetrieveInfo/View Info”, “Zoom”, “Rotate”, “Fit to Screen”, “Next Slide”, “PreySlide (if applicable), “Save Slide”, “Download Attachment”, “Help”,“Call Voice Mail”, etc. Additional operations can be performed inresponse to actuation of the trackball/touch input device 250, such asscrolling to a next (or previous) slide.

If the attachment has been previously requested (e.g., a “Yes” at 410),attachment server 119 can transcerpt and encapsulates the DOM in UCSdata, and transmit the UCS data to portable electronic device 112 inchunks, as indicated at 445, for display (450).

In some implementations, device 112 can perform one or more of DOM buildand UCS formatting, e.g., on presentation files stored on the device.

Upon selection of the “Present” command (500), the presentationapplication 319 is launched, as shown in FIG. 5. At 510, the applicationcan check to see that the presentation adapter 360 is connected. If not,a communication channel is established between portable electronicdevice 112 and presentation device 113, e.g. via a pairing connectionprocess (515) such as Bluetooth® wireless technology pairing. A typicalpairing connection process calls up a wizard for presenting steps toestablish communication pairing between the device 112 and presentationadapter 360 of the presentation device 113 using the communicationsapplications 305 and 365 (e.g. Bluetooth discovery and pairing). Otherwireless and wired communications technologies can be used between thedevice 112 and the presentation device 113.

At 520, the application 319 sends a session ID to the pairedpresentation adapter 360. The application then checks for slidepresentation data (e.g. a first UCS chunk representing the first slide)having already been transmitted to and locally stored at thepresentation adapter 360 (525). This can be accomplished, for example,by comparing check sums, or any other appropriate method. If not, thepresentation application 319 sends the slide data to the presentationadapter 360 (and, in some implementations, requesting additional datafrom the attachment server 119, as discussed above in connection withFIG. 4).

Referring to FIG. 6, methods 600 of the technology are illustrated. UCSdata representing a slide of a presentation is now stored in memory ofpresentation device 113, whether from the portable electronic device112, SD memory card of the presentation device 113, or otherwise. Thepresentation device 113 constructs the slide from the stored UCS data602 (typically a collection of objects, e.g., text, static graphics,animated graphics) to a format compatible with the targeted displaytechnology 190. Such processes can include, e.g., image decompression,text rendering, color conversion, setup of animation information for theslide. In some implementations of the presentation device 113, thedevice 113 includes UCS data processing memory allocated to textconstruction. The text construction memory 380 is sized to accommodate afull slide of text, e.g., filling a 1024×768 display. Processing of theUCS data in this fashion results in a constructed slide.

The constructed slide is rendered 604 to a region of presentation device113 memory allocated to direct display, e.g., a visible region in aready-to-display format, typically in response to an instruction from anelectronic device 112. Rendering the ready-to-display data in a visibleregion frees up memory space used during slide construction, e.g., thetext construction region. In typical presentation devices, the slideconstruction region remains unused until the presentation device 113receives UCS data for another slide, e.g., as a consequence of themobile device 112 receiving a command to transition to a slide of thepresentation that has not been stored as UCS data on the presentationdevice 113.

Implementations of the present technology anticipate the next slide tobe presented 606. If the UCS data for the anticipated slide is notstored on the presentation device, some implementations can request theUCS data for the anticipated slide 608. After receiving the anticipatedslide UCS data 610, whether by request or otherwise (and preferablyafter copying any earlier-constructed slide to a visible region ofpresentation device 113 memory), implementations of the technologyconstruct the anticipated slide 612. The constructed anticipated slideis cached and pre-drawn into the memory space allocated to slideconstruction 614. In this fashion, the anticipated slide is ready forcopying to a visible region (e.g., main buffer, flip buffer undercontrol of a video driver) of presentation device 113 memory.

In some implementations, the anticipated slide is the next slide insequence in the presentation. In some implementations, the anticipatedslide can be determined from slide metadata, e.g., the title slide, theheading slide of a next presentation section, the slide that has beendisplayed the most times during the presentation, the slide that hasbeen displayed for the longest period of time during the presentation,etc. In some implementations, the memory space otherwise allocated toslide construction that is used to pre-draw the anticipated slide can bethe text construction memory 380.

When the presentation device 113 is instructed to proceed to a slidedifferent than the one currently being made available for display 616,the presentation device can determine if the cache holds the constructednew slide and if the new slide is pre-drawn in construction memory 618,i.e., if the anticipated slide is the slide for which it received a newdisplay instruction. If so, then the presentation device 113 can copythe pre-drawn anticipated slide into the visible portion of memory(display memory 390), and use the cached constructed anticipated slidefor rendering the new slide as necessary 620. In this fashion, thepresentation device 113 can reduce the latency between slides when theanticipated slide is the new slide that the presentation device isinstructed to display.

In some implementations, slide construction is a higher-priority usethan slide caching for the memory used for slide caching. In thoseimplementations, when the presentation device 113 has a slideconstruction task, that task takes priority over slide caching.

The present technology can take the forms of hardware, software or bothhardware and software elements. In some implementations, the technologyis implemented in software, which includes but is not limited tofirmware, resident software, microcode, a Field Programmable Gate Array(FPGA) or Application-Specific Integrated Circuit (ASIC), etc. Inparticular, for real-time or near real-time use, an FPGA or ASICimplementation is desirable.

Furthermore, the present technology can take the form of a computerprogram product comprising program modules accessible fromcomputer-usable or computer-readable medium storing program code for useby or in connection with one or more computers, processors, orinstruction execution system. For the purposes of this description, acomputer-usable or computer readable medium can be any apparatus thatcan contain, store, communicate, propagate, or transport the program foruse by or in connection with the instruction execution system,apparatus, or device. The medium can be an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system (orapparatus or device) or a propagation medium (though propagation mediumsin and of themselves as signal carriers are not included in thedefinition of physical computer-readable medium). Examples of a physicalcomputer-readable medium include a semiconductor or solid state memory,magnetic tape, a removable computer diskette, a random access memory(RAM), a read-only memory (ROM), a rigid magnetic disk and an opticaldisk. Current examples of optical disks include compact disk—read onlymemory (CD-ROM), compact disk—read/write (CD-R/W) and DVD. Bothprocessors and program code for implementing each as aspect of thetechnology can be centralized or distributed (or a combination thereof)as known to those skilled in the art.

A data processing system suitable for storing a computer program productof the present technology and for executing the program code of thecomputer program product will include at least one processor coupleddirectly or indirectly to memory elements through a system bus. Thememory elements can include local memory employed during actualexecution of the program code, bulk storage, and cache memories thatprovide temporary storage of at least some program code in order toreduce the number of times code must be retrieved from bulk storageduring execution. Input/output or I/O devices (including but not limitedto keyboards, displays, pointing devices, etc.) can be coupled to thesystem either directly or through intervening I/O controllers. Networkadapters can also be coupled to the system to enable the data processingsystem to become coupled to other data processing systems or remoteprinters or storage devices through intervening private or publicnetworks. Modems, cable modem and Ethernet cards are just a few of thecurrently available types of network adapters. Such systems can becentralized or distributed, e.g., in peer-to-peer and client/serverconfigurations. In some implementations, the data processing system isimplemented using one or both of FPGAs and ASICs.

Referring to FIG. 7, a data processing system (e.g., 700) suitable forstoring a computer program product of the present technology and forexecuting the program code of the computer program product can includeat least one processor (e.g., processor resources 712) coupled directlyor indirectly to memory elements through a system bus (e.g., 718comprising data bus 718 a, address bus 718 b, and control bus 718 c).The memory elements can include local memory (e.g., 716) employed duringactual execution of the program code, bulk storage (e.g., 760), andcache memories (e.g., including cache memory as part of local memory orintegrated into processor resources) that provide temporary storage ofat least some program code in order to reduce the number of times codemust be retrieved from bulk storage during execution. Input/output orI/O devices (including but not limited to keyboards 750, displays 730,pointing devices 720, etc.) can be coupled to the system either directlyor through intervening I/O controllers (e.g., 714). Network adapters canalso be coupled to the system to enable the data processing system tobecome coupled to other data processing systems or remote printers orstorage devices through intervening private or public networks. Modems,cable modem and Ethernet cards are just a few of the currently availabletypes of network adapters. Such systems can be centralized ordistributed, e.g., in peer-to-peer and client/server configurations. Insome implementations, the data processing system is implemented usingone or both of FPGAs and ASICs.

The invention claimed is:
 1. A computer-implemented method for slidepresentation, the method comprising: automatically anticipating anon-consecutive slide to be selected for display on a presentationdevice based on slide metadata; receiving, from an attachment server,complete Universal Content Stream text and graphics data of theanticipated slide in an unconstructed format; constructing, at thepresentation device, the anticipated slide from the received data viaimage decompression, text rendering and color conversion processing;caching the constructed slide in a cache of the presentation device;pre-drawing the constructed slide in text construction memory of thepresentation device; receiving instructions to display a slide which isnot a slide currently available for display; and in the event that theinstructed slide is the cached and pre-drawn slide, rendering thepre-drawn slide to display memory of the presentation device.
 2. Thecomputer-implemented method of claim 1 wherein: anticipating comprisesdetermining the slide most frequently-presented during a currentpresentation.
 3. The computer-implemented method of claim 1 wherein:anticipating comprises determining the title slide of a currentpresentation.
 4. The computer-implemented method of claim 1 wherein:anticipating comprises determining the slide longest displayed during acurrent presentation.
 5. The computer-implemented method of claim 1wherein: caching the constructed slide is a lower priority activity thanconstructing another slide.
 6. A computer program product for slidepresentation, the computer program product comprising: at least onenon-transitory computer readable medium; and at least one programmodule, stored on the at least one medium, and operative, upon executionby at least one processor for: automatically anticipating anon-consecutive slide on a display device based on slide metadata;receiving from an attachment server, complete Universal Content Streamtext and graphics data of the anticipated slide in an unconstructedformat; constructing, at the display device, the anticipated slide fromthe received data via image decompression, text rendering and colorconversion processing; caching the constructed slide in a cache of thedisplay device; pre-drawing the constructed slide in text constructionmemory of the display device; receiving instructions to display a slidewhich is not a slide currently available for display; and in the eventthat the instructed slide is the cached and pre-drawn slide, renderingthe pre-drawn slide to display memory of the display device.
 7. Thecomputer program product of claim 6, wherein: anticipating comprisesdetermining the slide most frequently-presented during a currentpresentation.
 8. The computer program product of claim 6 wherein:anticipating comprises determining the title slide of a currentpresentation.
 9. The computer program product of claim 6 wherein:anticipating comprises determining the slide longest displayed during acurrent presentation.
 10. The computer program product of claim 6wherein: caching the constructed slide is a lower priority activity thanconstructing another slide.
 11. A system for slide presentation on aportable electronic device, the system comprising: at least oneprocessor within the portable electronic device, at least one computerreadable medium in communication with the processor; at least oneprogram module, stored on the at least one medium, and operative uponexecution by the processor for: automatically anticipating anon-consecutive slide to be selected for display based on slidemetadata; receiving from an attachment server, complete UniversalContent Stream text and graphics data of the anticipated slide in anunconstructed format; constructing, at the portable electronic device,the anticipated slide from the received data via image decompression,text rendering and color conversion processing; caching the constructedslide in a cache of the portable electronic device; pre-drawing theconstructed slide in text construction memory of the portable electronicdevice; receiving instructions to display a slide which is not a slidecurrently available for display; and in the event that the instructedslide is the cached and pre-drawn slide, rendering the pre-drawn slideto display memory of the portable electronic device.
 12. The system ofclaim 11, wherein: anticipating comprises determining the slide mostfrequently-presented during a current presentation.
 13. The system ofclaim 11 wherein: anticipating comprises determining the title slide ofa current presentation.
 14. The system of claim 11 wherein: anticipatingcomprises determining the slide longest displayed during a currentpresentation.
 15. The system of claim 11 wherein: caching theconstructed slide is a lower priority activity than constructing anotherslide.